Skip to content

chore(deps): update dependency typescript to v6#4448

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/typescript-6.x
Open

chore(deps): update dependency typescript to v6#4448
renovate[bot] wants to merge 1 commit intomainfrom
renovate/typescript-6.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 27, 2026

This PR contains the following updates:

Package Change Age Confidence
typescript (source) ~5.9.0~6.0.0 age confidence

Release Notes

microsoft/TypeScript (typescript)

v6.0.2

Compare Source


Configuration

📅 Schedule: Branch creation - "every weekday before 11am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner March 27, 2026 05:08
@renovate renovate bot requested a review from gnbm March 27, 2026 05:08
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Mar 27, 2026

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: static/code/stackblitz/v8/angular/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @angular-devkit/build-angular@20.3.17
npm error Found: typescript@6.0.2
npm error node_modules/typescript
npm error   dev typescript@"~6.0.0" from the root project
npm error   peerOptional typescript@">=4.9.5" from cosmiconfig@9.0.0
npm error   node_modules/cosmiconfig
npm error     cosmiconfig@"^9.0.0" from postcss-loader@8.1.1
npm error     node_modules/postcss-loader
npm error       postcss-loader@"8.1.1" from @angular-devkit/build-angular@20.3.17
npm error       node_modules/@angular-devkit/build-angular
npm error         dev @angular-devkit/build-angular@"^20.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=5.8 <6.0" from @angular-devkit/build-angular@20.3.17
npm error node_modules/@angular-devkit/build-angular
npm error   dev @angular-devkit/build-angular@"^20.0.0" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peer typescript@">=5.8 <6.0" from @angular-devkit/build-angular@20.3.17
npm error   node_modules/@angular-devkit/build-angular
npm error     dev @angular-devkit/build-angular@"^20.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-03-27T15_07_54_329Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-27T15_07_54_329Z-debug-0.log

File name: static/code/stackblitz/v7/angular/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @angular-devkit/build-angular@20.3.17
npm error Found: typescript@6.0.2
npm error node_modules/typescript
npm error   dev typescript@"~6.0.0" from the root project
npm error   peerOptional typescript@">=4.9.5" from cosmiconfig@9.0.0
npm error   node_modules/cosmiconfig
npm error     cosmiconfig@"^9.0.0" from postcss-loader@8.1.1
npm error     node_modules/postcss-loader
npm error       postcss-loader@"8.1.1" from @angular-devkit/build-angular@20.3.17
npm error       node_modules/@angular-devkit/build-angular
npm error         dev @angular-devkit/build-angular@"^20.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=5.8 <6.0" from @angular-devkit/build-angular@20.3.17
npm error node_modules/@angular-devkit/build-angular
npm error   dev @angular-devkit/build-angular@"^20.0.0" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peer typescript@">=5.8 <6.0" from @angular-devkit/build-angular@20.3.17
npm error   node_modules/@angular-devkit/build-angular
npm error     dev @angular-devkit/build-angular@"^20.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-03-27T15_08_02_891Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-27T15_08_02_891Z-debug-0.log

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 27, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
ionic-docs Ready Ready Preview, Comment Mar 27, 2026 3:10pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants